Skip to content

Conversation

@woodruffw
Copy link
Member

@woodruffw woodruffw commented Jan 5, 2026

WIP, needs a release of packaging to unblock.

Once there's a new packaging release:

  • Bump here
    • Release candidate
    • Full packaging release
  • Update the tests
    • test_metadata
    • test_legacy

See: pypa/packaging#950

Closes #19083.

Signed-off-by: William Woodruff <[email protected]>
@woodruffw woodruffw self-assigned this Jan 5, 2026
@woodruffw woodruffw added the metadata Issues associated with Project/Release/File metadata label Jan 5, 2026
@woodruffw
Copy link
Member Author

I've bumped to 26.0rc2 for testing purposes. This caused a lot of problems for the other locked requirements (e.g. in make checkdb), so I've (temporarily?) used main.in as a constraint file for all of the pip-compile invocations.

Signed-off-by: William Woodruff <[email protected]>
Signed-off-by: William Woodruff <[email protected]>
Comment on lines +298 to +299
"import_names": "import_name",
"import_namespaces": "import_namespace",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Flagging: IIUC the form representation of metadata is only used for sdists prior to 2.2, so I think we technically don't need this. However, I noticed that we also have 2.4 fields here (licence_file{,s}) so I wasn't sure.

(Others are missing however, like license_expression{,s}.)

Signed-off-by: William Woodruff <[email protected]>
Signed-off-by: William Woodruff <[email protected]>
Signed-off-by: William Woodruff <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

metadata Issues associated with Project/Release/File metadata

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support Core Metadata 2.5 (PEP 794, Import-Name, Import-Namespace)

2 participants